home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.smalltalk,comp.lang.perl.misc,comp.lang.pascal.borland,comp.lang.eiffel,comp.lang.cobol,comp.lang.c++.leda,comp.lang.c,comp.lang.basic.visual.3rdparty,alt.computer.workshop.live,alt.comp.hardware.homebuilt,alt.clearing.technology,alt.chinese.computing,news.newusers.questions
- Subject: Re: PROGRAMERS OF ANY LANGUAGE
- Date: 9 Apr 1996 19:50:54 -0700
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4kf7meINN5k0@keats.ugrad.cs.ubc.ca>
- References: <Pine.SOL.3.91.960329010021.13209A-100000@harvey> <4k4pl2$pea@host1.einstein.com.ar> <316A6189.4287@wight.hursley.ibm.com> <4kebqq$4qs@Starbase.NeoSoft.COM>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4kebqq$4qs@Starbase.NeoSoft.COM>,
- Will Morse <will@Starbase.NeoSoft.COM> wrote:
- >I like to use {/} because vi, among others, lets me find the matching
- >}/{ using the % key.
-
- It's not impossible to match begin/end in the same way. The vi editor I use,
- Vim, matches #ifdef/#else/#endif directives by jumping among the three.
-
- Vi matches { } because it was designed by a C/UNIX programmer.
- --
-
-